Feature/inject namespace required for kustomize #24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Pull Request Description
Motivation
This pull request introduces the necessary changes to inject the namespace required for Kustomize into the Kerberos.io Helm charts. By explicitly defining the namespace for each resource, we ensure that the Helm charts are compatible with Kustomize and can be deployed consistently across different environments. This change enhances the flexibility and robustness of our deployment process.
Changes Overview
Namespace Injection:
namespace: {{ .Release.Namespace }}
to all relevant Kubernetes resource templates within the Helm charts. This ensures that resources are created in the correct namespace as specified during the Helm release.Ingress Class Annotation Update:
kubernetes.io/ingress.class
annotation withingressClassName
to align with the latest Kubernetes best practices.Version Bump:
0.74.0
to0.75.0
to reflect the changes and ensure proper versioning for Helm deployments.Documentation Fix:
Benefits
ingressClassName
ensures compatibility with current and future Kubernetes versions.By implementing these changes, we improve the overall deployment process, making it more reliable and adaptable to various deployment tools and environments.